Systems and methods to facilitate task-specific workspaces for a collaboration work management platform

ABSTRACT

Described herein are systems and methods to facilitate task-specific workspaces for a collaboration work management platform. Task-specific workspaces for individual ones of the users for individual ones of the tasks may be facilitated. Presentation of the first task and/or the first task-specific workspace for the first task for the first user may be effectuated. Information characterizing interactions of the first user with the first set of applications within the first task-specific workspace at or near a first time may be obtained and/or stored responsive to a pause and/or completion of the first task at the first time. The one or more windows corresponding to the first set of applications for the first task may be minimized and/or closed. Responsive to a re-start of the first task, the first set of applications may be restored based on the environment state information.

FIELD

The disclosure relates to systems and methods to facilitatetask-specific workspaces for a collaboration work management platform.

BACKGROUND

Generic computer interfaces offer few if any options for limitingdistractions. Employees often lose time, efficiency, and/or focusbecause of interruptions, distractions, switching between tasks andlosing their place/train of thought, etc. Existing interfaces fail tooffer clean workspaces that enable a user to transition between tasksefficiently, without losing their work and/or place. Existing managementplatforms and/or interfaces often offer too many choices and/or optionsthat make it difficult to actually get work done because users areoverwhelmed and/or distracted by the interface.

SUMMARY

The disclosure relates to systems and methods configured to facilitatetask-specific workspaces for a collaboration work management platform.The task-specific workspaces may provide a focused workspace in whichusers can work with fewer distractions. The applications and/or windowsopen within the task-specific workspace may be related to and/or usedfor working on a specific task such that users are not distracted bywindows and/or applications that are unrelated to the task they arecurrently working on. When the users pause the task within the taskspecific workspace and/or switch tasks, the state of the task-specificworkspace and/or the user's interactions with the windows and/orapplications within the task-specific workspace may be saved. As such,the user may be able to return to where they left off within thetask-specific workspace at a later time. By way of non-limiting example,if a user pauses a task within a task-specific workspace while workingwithin a word document, an internet browser, and/or a presentationapplication, the state of the word document, the internet browser,and/or the presentation application may be saved such that when the userre-starts and/or re-selects the task, the applications and/or windowscorresponding to the word document, the internet browser, and/or thepresentation application automatically open. The applications and/orwindows corresponding to the word document, internet browser, and/orpresentation application may automatically open in the same arrangementand/or to the same section of the word document, internet webpage,and/or slide the user was working on at or near the time they paused thetask and/or switched tasks.

The task-specific workspaces may takeover a desktop of a user. The usermay be presented with one or more tasks (e.g., a task list, etc.) ratherthan all of the different applications and/or documents that aretypically presented with existing desktops. This may clutter thedesktop, overwhelm the user, and/or distract the user from the tasksthey need to complete. Users often work from various different devices(e.g., multiple computers, mobile devices, etc.) having to save thingslocally and/or transfer them from one device to another. Task-specificworkspaces automatically track and maintain the state of the workspacesuch they the user could pick up where they previously left off on thesame device and/or across different devices. This reduces the need tosave things locally on devices, eliminates extra steps of uploadingsaved documents to a file-share program and/or emailing saved documents,and solves the problems associated with lost time getting users up tospeed and/or picking up where they left off.

The presentation of the collaboration environment may be based onenvironment state information. The storage component may be configuredto effectuate storage of the environmental state information. Theenvironmental state information may define the state of thecollaboration environment. The state of the collaboration environmentmay comprise a user state, a project state, a task state, and/or orother states that make up the collaboration environment state. Theenvironmental state information may include one or more records. The oneor more records may include one or more user records, project records,task records, and/or other records. The user state may be defined by oneor more of the user records. The user records may define values of userparameters associated with users interacting with, viewing, and/or ableto interact with or view the collaboration environment. The projectstate may be defined by the project records. The project records maydefine values of project parameters for projects managed within thecollaboration environment. The task state may be defined by the taskrecord. The task record may define values of task parameters for taskscreated and/or assigned within the collaboration environment.

In some implementations, a system configured to facilitate task-specificworkspaces for a collaboration work management platform may include oneor more of: one or more servers, one or more client computing platforms,and/or other components. The one or more servers may be configured tocommunicate with one or more client computing platforms according to aclient/server architecture and/or other architecture. The one or moreservers and/or client computing platforms may include one or morephysical processors configured to execute one or more computer programcomponents. The computer program components may include one or more ofan environment state component, a collaboration environment component, auser task component, a desktop component, a workspace component, anapplication component, and/or other components.

The one or more client computing platform(s) may be configured tofacilitate task-specific workspaces for individual ones of the users forindividual tasks. The one or more tasks may include action items, to-doitems, and/or objectives within a given project managed via thecollaboration work management platform. The one or more tasks may beassigned to one or more users such that the one or more tasks assignedto a given user may appear on a given user's task list within thecollaboration environment.

User task component may be configured to receive user input indicatingselection of a first task. User task component may be configured toeffectuate presentation of the first task for the first user.Presentation of the first task for the first user may be based on theenvironment state information. Responsive to the first user selectingthe first task, the user task component may be configured to requestinformation associated with the first task (e.g., a first user record, afirst project record, a first task record, and/or other information)from the server. The server may effectuate transmission of the firstuser record, the first project record, the first task record, and/orother records over the network to the user task component.

In some implementations, desktop component may be configured to clearthe current desktop of a given client computing platform. The desktopmay be cleared to initiate a clean workspace (e.g., a firsttask-specific workspace) for the first task.

The workspace component may be configured to effectuate presentation ofthe first task-specific workspace for the first task. In someimplementations, a first set of applications may be accessible by thefirst user via the first task-specific workspace. The first set ofapplications may have one or more corresponding windows through whichthe first user interacts with the first set of applications. The firstuser may work on the first task using one or more applications in thefirst set of applications.

The workspace component may be configured to block and/or restrict oneor more applications within the task-specific workspace. As such, one ormore other applications generally available via the first clientcomputing platform outside of the task-specific workspace, may notaccessible within the first task-specific workspace.

The workspace component may be configured to receive user inputindicating a pause and/or completion of the first task at a first time.By way of example, a pause of the first task may be indicated byswitching to a second task and/or another task. The applicationcomponent may be configured to obtain information characterizinginteractions of the users with the applications within the task-specificworkspaces at or near the time the task is paused. In someimplementations, the application component may be configured to obtaininformation characterizing interactions of the first user with the firstset of applications within the first task-specific workspace at or nearthe first time. The interactions may include, for example, informationindicating which applications the user had open, which webpage(s) and/orfile(s) the user had open, the application and/or document titles theuser was working on and/or had open, progress information characterizingprogress of the first user within the first set of applications (e.g.,where the user left off in one or more webpages and/or files), and/or onthe first task (e.g., the user paused the task when 60% completed), anamount of time spent on active applications and/or webpages, and/orother interactions.

The application component may be configured to store the informationcharacterizing the interactions of the first user with the first set ofapplications at or near the first time. The information characterizingthe interactions of the first user with the first set of applications ator near the first time may be stored as part of a first user recordand/or a first task record. The workspace component may be configured tominimize and/or close the one or more windows corresponding to the firstset of applications for the first task responsive to the receiving theuser input indicating the first task is paused and/or completed.

Responsive to a user re-opening and/or re-starting the first task and/orthe first task-specific workspace, the workspace component may beconfigured to restore the first set of applications based on theenvironment state information. The first set of applications and/or theone or more windows corresponding to the first set of applications maybe restored (e.g., re-opened, re-arranged, reverted, etc.) based on thefirst user record and/or the first task record.

These and other objects, features, and characteristics of the systemand/or method disclosed herein, as well as the methods of operation andfunctions of the related elements of structure and the combination ofparts and economies of manufacture, will become more apparent uponconsideration of the following description and the appended claims withreference to the accompanying drawings, all of which form a part of thisspecification, wherein like reference numerals designate correspondingparts in the various figures. It is to be expressly understood, however,that the drawings are for the purpose of illustration and descriptiononly and are not intended as a definition of the limits of theinvention. As used in the specification and in the claims, the singularform of “a”, “an”, and “the” include plural referents unless the contextclearly dictates otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system configured to facilitate task-specificworkspaces for a collaboration work management platform, in accordancewith one or more implementations.

FIG. 2A illustrates an exemplary graphical user interface for initiatinga task-specific workspace, in accordance with one or moreimplementations.

FIG. 2B illustrates an exemplary application recommendation interfacefor a task-specific workspace, in accordance with one or moreimplementations.

FIG. 2C illustrates an exemplary task-specific workspace, in accordancewith one or more implementations.

FIG. 2D illustrates an exemplary graphical user interface for pausing atask-specific workspace, in accordance with one or more implementations.

FIG. 3 illustrates a method to facilitate task-specific workspaces for acollaboration work management platform, in accordance with one or moreimplementations.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 100 configured to facilitate task-specificworkspaces for a collaboration work management platform, in accordancewith one or more implementations. In some implementations, system 100may be configured to effectuate presentation of a collaborationenvironment based on environment state information. Users may viewand/or interact with the collaboration environment. One or more projectsmay be managed within the collaboration environment. One more tasks maybe created and/or assigned to one or more users within the collaborationenvironment.

The presentation of the collaboration environment may be based onenvironment state information. The environment state information mayinclude user records 128, project records 130, task records 132, and/orother records. The environment state information may be continuouslygenerated and/or updated based on the state of the collaborationenvironment representing the users' interactions with the collaborationenvironment. The state of the collaboration environment may include auser state, a project state, a task state, and/or other states. The userstate may be defined by user records 128. User records 128 may definevalues of user parameters associated with users interacting with and/orviewing the collaboration environment. The project state may be definedby project records 130. Project records 130 may define values of projectparameters for projects managed within the collaboration environment.The task state may be defined by task records 132. Task records 132 maydefine values of task parameters for tasks created and/or assignedwithin the collaboration environment.

The user parameters associated with the users interacting with and/orviewing the collaboration environment may include parameters describingthe users, their actions within the collaboration environment, theirsettings, and/or other user information; and/or metadata associated withthe users, their actions within the environment, their settings, and/orother user information. Individual ones of the users may be associatedwith individual ones of the user records. A user record may definevalues of the user parameters associated with a given user interactingwith and/or viewing the collaboration environment.

The user parameters may, by way of non-limiting example, include one ormore of: a user name, a user role, a user department, descriptive usercontent, a to-email, a from-email, a photo, an organization, aworkspace, one or more projects (which may include project parametersdefined by one or more project records); one or more tasks (which mayinclude one or more task parameters defined by one or more taskrecords), one or more user comments, one or more teams the user belongsto, one or more of the user display settings (e.g., colors, size,project order, task order, etc.), one or more authorized applications,one or more presence/interaction parameters (e.g., indicating presenceand/or interaction level at an environment level, project level, taskall, application level, etc.), one or more notification settings, one ormore progress parameters, status information for one or more tasks theuser is associated with, one or more statistics related to a given user(e.g., how many tasks the user has completed, how quickly the usercompleted the tasks, the efficiency of the user, bandwidth of the user,activity level of the user, etc.), application access information (e.g.,username/password for one or more third-party applications), one or morefavorites and/or priorities, other user parameters for the given user,and/or other user parameters, project parameters, and/or task parametersfor one or more projects and/or tasks the given user is associated with.

The project parameters for projects managed within the collaborationenvironment may include parameters describing one or more projectsmanaged within the collaboration environment and/or via thecollaboration work management platform, and/or the metadata associatedwith the one or more projects. Individual ones of the projects may beassociated with individual ones of the project records. A project recordmay define values of the project parameters associated with a givenproject managed within the collaboration environment and/or via thecollaboration work management platform. A given project may have one ormore owners and/or one or more team members working on the givenproject. The given project may include one or more tasks assigned to oneor more users under the given project heading.

The project parameters may, by way of non-limiting example, include oneor more of: one or more tasks within individual ones of the projects(which may include task parameters defined by one or more task records),one or more user comment parameters (e.g., a creator, a recipient, oneor more followers, one or more other interested parties, content, one ormore times, upvotes, other hard-coded responses, etc.), a project name,a project description, one or more project dates (e.g., a start date, adue date, a completion date, and/or other project dates), one or moreproject members (e.g., an owner, one or more other project members,member access information, and/or other project members and/or memberinformation), a status and/or progress (e.g., an update, a hardcodedstatus update, a measured status, quantity of tasks remaining in a givenproject, completed tasks in a given project, and/or other statusparameter), one or more attachments, notification settings, privacy, anassociated URL, one or more interaction parameters (e.g., sources of theinteractions, context of the interactions, content of the interactions,time for the interactions, and/or other interaction parameters),updates, ordering of tasks within the given project, state of aworkspace for a given task within the given project, other projectparameters for the given project, and/or other project parameters, userparameters, and/or task parameters for one or more users and/or tasksthe given project is associated with.

The task parameters for tasks within the collaboration environment mayinclude parameters describing one or more tasks created and/or assignedwithin the collaboration environment and/or via the collaboration workmanagement platform, and/or the metadata associated with the one or moretasks. Individual ones of the tasks may be associated with individualones of the tasks records. A task record may define values of the taskparameters associated with a given task created and/or assigned withinthe collaboration environment and or via the collaboration workmanagement platform. The tasks make include one or more to-do items,action items, objectives, and/or other tasks one or more users shouldand/or plan on accomplishing. Tasks may be created by a given user forthe given user and/or created by the given user and assigned to one ormore other users.

The task parameters may, by way of non-limiting example, include one ormore of: a task name, a task a description, a task status (e.g.,complete, incomplete, and/or another status), an assignee, one or morefollowers, one or more team members, one or more task dates (e.g., astart date, a completion date, a due date, and/or other dates), one ormore user comment parameters (e.g., a creator, a recipient, one or morefollowers, one or more other interested parties, content, one or moretimes, upvotes, other hard-coded responses, etc.), task upvotes, otherhard-coded task responses, one or more tags, one or more custom fields(e.g., priority, cost, stages, and/or other custom fields), one or moredependencies (e.g., tasks dependent on, dependent tasks. Users assignedto dependent tasks, notification settings for dependent tasks, and/orother dependencies), a task URL, one or more subtasks and/or subtaskparameters (e.g., name, description, hardcoded status, assignees, duedate, state date, comments, upvotes, tags, and/or other subtaskparameters), one or more attachments, one or more interaction parameters(e.g., sources of the interactions, context of the interactions, contentof the interactions, time for the interactions, and/or other interactionparameters), state of a workspace for a given task (e.g., applicationstate parameters, application status, application interactions, userinformation, and/or other parameters related to the state of theworkspace for a given task), other task parameters for the given task,and/or other task parameters, user parameters, and/or project parametersfor one or more users and/or project(s) the given task is associatedwith.

It is noted that any metadata and/or values of parameters related to anyusers, projects, and/or tasks may be considered values of userparameters, project parameters, and/or task parameters. The terms “userparameters”, “project parameters”, and/or “task parameters” may be usedinterchangeably herein.

As is illustrated in FIG. 1, system 100 may include one or more of: oneor more servers 102, one or more client computing platforms 124,external resources 122, and/or other components. Users may interact withsystem 100 via one or more client computing platforms 124. The one ormore servers 102 may be configured to communicate with one or moreclient computing platforms 124 according to a client/server architectureand/or other communication schemes. The one or more client computingplatforms 124 may include one or more of a cellular telephone, asmartphone, a digital camera, a laptop, a tablet computer, a desktopcomputer, a television set-top box, smart TV, a gaming console, and/orother client computing platforms.

The one or more servers 102 may include one or more physical processors104 and/or physical processors 105 (also referred to herein as “one ormore processors” and/or “processor(s)”), non-transitory electronicstorage 126, and/or other components. Non-transitory electronic storage126 may include one or more records. The one or more records may storethe environment state information that defines the state of thecollaboration environment. The state of the collaboration environmentmay include a user state, a project state, a task state, and/or otherstates. The records may include user records 128, project records 130,task records 132, and/or other records. The one or more physicalprocessors 104 may be configured to access one or more of user records128, project records 130, task records 132, and/or other records toeffectuate transmission of the environment state information overnetwork 132 to client computing platform(s) 124. Client computingplatform(s) 124 may use the environment state information to effectuatepresentation of the collaboration environment via client computingplatform(s) 124. The one or more physical processors 104 and/or physicalprocessors 105 may be configured to execute machine-readableinstructions 106 and/or machine-readable instructions 107. Themachine-readable instructions 106 may include one or more computerprogram components. The computer program components may include one ormore of an environment state component 108, a collaboration environmentcomponent 110, a user task component 112, a desktop component 114, aworkspace component 116, an application component 118, a and/or othercomponents.

In some implementations, server(s) 102 may be configured to provideremote hosting of the features and/or functions of machine-readableinstructions 106 to one or more client computing platform(s) 124 thatmay be remotely located from server(s) 102. In some implementations, oneor more features and/or functions of server(s) 102 may be attributed aslocal features and/or functions of one or more client computingplatform(s) 124. For example, individual ones of the client computingplatform(s) 124 may include one or more additional machine-readableinstructions 107 comprising the same or similar components asmachine-readable instructions 106 of server(s) 102. The client computingplatform(s) 124 may be configured to locally execute the one or morecomponents that may be the same or similar to the machine-readableinstructions 106. One or more features and/or functions ofmachine-readable instructions 106 of server(s) 102 may be provided, atleast in part, as an application program that may be executed at a givenclient computing platform 124. One or more features and/or functions ofmachine-readable instructions 107 may be provided, at least in part, ata server(s) 102.

The electronic storage 126 may include electronic storage media thatelectronically stores information. The electronic storage media ofelectronic storage 126 may include one or both of system storage that isprovided integrally (i.e., substantially non-removable) with one or moreservers 102 and/or removable storage that is removably connected to oneor more servers 102. The connection may be facilitated by, for example,a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., adisk drive, etc.). The electronic storage 126 may include one or more ofoptically readable storage media (e.g., optical disks, etc.),magnetically readable storage media (e.g., magnetic tape, magnetic harddrive, floppy drive, etc.), electrical charge-based storage media (e.g.,EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.),and/or other electronically readable storage media. The electronicstorage 126 may include one or more virtual storage resources (e.g.,cloud storage, a virtual private network, and/or other virtual storageresources). The electronic storage 126 may store software algorithms,information determined by processor(s) 104, information received by oneor more servers 102, information received by client computing platforms124, and/or other information that enables one or more servers 102 tofunction as described herein.

The electronic storage 126 may be configured to store one or morerecords and/or information. The one or more records may include one ormore of user records 128, project records 130, task records 132, and/orother records.

The one or more records (e.g., user records 128, project records 130,task records 132, and/or other records) may specify and or define valuesfor one or more user parameters, project parameters, and/or otherparameters for the collaboration environment. The one or more recordsmay specify correspondences between one or more of the user records 128,project records 130, task records 132, and/or other records. Thecorrespondences may be used to determine which user parameters and/orvalues, project parameters and/or values, and/or task parameters and/orvalues are associated with a given user, project, and/or task within thecollaboration environment.

The client computing platform(s) 124 may monitor, and/or collectinformation for transmission to the one or more server(s) 102 to bestored as environment state information. The client computingplatform(s) 124 may obtain and/or collect environment state informationfrom the one or more server(s) 102.

The environment state component 108 of machine-readable instructions 106may be configured to effectuate transmission of the environment stateinformation to client computing platform(s) 124, and/or vice versa. Insome implementations, environment state component 108 may be configuredto receive information over network 132 from client computingplatforms(s) 124. Environment state component 108 may be configured toeffectuate storage of the received information as environment stateinformation to one or more user records 128, project records 130, taskrecords 132, and/or other records. Environment state component 108 maybe configured to obtain one or more user records 128, project records130, task records 132, and/or other records in response to and/or basedon one or more requests from client computing platform(s) 124.Environment state component 108 may be configured to effectuatetransmission of values for user parameters, values for projectparameters, values for task parameters, and/or other state informationto client computing platform(s) 124. The values for user parameters,values for project parameters, values for task parameters, and/or otherstate information may be used to effectuate presentation of the relevanttasks and/or projects for a given user of the collaboration environmentassociated with the given client computing platform 124 to which thevalues and/or other state information is transmitted.

Collaboration environment component 110 of machine-readable instructions107 may be configured to effectuate presentation of a collaborationenvironment. Presentation of the collaboration environment may be basedon environment state information. The environment state information mayinclude user records, project records, task records, and/or otherrecords. The environment state information may define a state of thecollaboration environment. The state of the collaboration environmentmay include a user state, a project state, a task state, and/or otherstates. The user state may be defined by the user records. The userrecords may define values of user parameters associated with usersinteracting with and/or viewing the collaboration environment. Theproject state may be defined by the project records. The project recordsmay define values of project parameters for projects managed within thecollaboration environment. The task state may be defined by the taskrecords. The task records may define values of task parameters for taskscreated and/or assigned within the collaboration environment.

The client computing platform(s) 124 may effectuate presentation of thecollaboration environment. The collaboration environment may include theenvironment in which users interact with and/or view the one or moretasks and/or projects managed via the collaboration work managementplatform. The collaboration environment may exist whether or not a givenuser is viewing and/or interacting with the collaboration environment.In some implementations, projects managed vie the collaborationenvironment may include one or more tasks. By way of non-limitingexample, the one or more tasks may include action items, to-do items,and/or objectives within a given project. The one or more tasks may beassigned to one or more users such that the one or more tasks assignedto a given user may appear on a given user's task list within thecollaboration environment. The one or more client computing platform(s)124 may be configured to facilitate task-specific workspaces forindividual ones of the users for individual ones of the tasks.

User task component 112 may be configured to receive user inputindicating selection of a task. In some implementations, wherein a firsttask-specific workspace is facilitated for a first user on a firstclient computing platform, the user input may indicate selection of afirst task. User input may include any input and/or indication by a userto start and/or work on the first task. In some implementations, usertask component 112 may effectuate presentation of multiple tasksassociated with the first user (e.g., assigned to the first user). Usertask component 112 may be configured to obtain user input indicating aselection of the first task from the multiple tasks.

In some implementations, user task component 112 may be configured todetermine a recommended task (e.g., which task a user should work on)based on the environment state information. The recommended task may bedetermined, for example, based on the due date, one or more dependenciesof the recommended tasks, efficiency and/or time information associatedwith the given user and/or task (e.g., it is 3 pm and task one ispredicted to take the user 2 hours to complete while task two ispredicted to take the user 4 hours to complete, the first task may berecommended if, for example, the user typically becomes inactive in thecollaboration environment after 5:00 p.m.), one or more other tasksassociated with the given user (e.g., the user has 4 other tasks duetomorrow), and/or other information.

In some implementations, user task component 112 may be configured todetermine and/or effectuate presentation of one or more recommendedapplications, documents, updates, and/or other information for workingon the first task. The one or more recommended applications, documents,updates, and/or other information may be presented and/or determinedresponsive to receiving user input indicating selection of the firsttask. The one or more recommended applications may be determined basedon user information (e.g., historical user information, userpreferences, etc.); task information (e.g., a type of task, the tasktitle, the task due date, etc.); generated work, documents, applicationsused, and/or other information from one or more dependent tasks, similartasks, associated tasks, and/or tasks that are otherwise linked to task;one or more updates, interactions, and/or events within a given task,project, and/or task-specific workspace; and/or one or more updates,interactions, and/or events within a given task, project, task-specificworkspace that occurred while the given user was not in thetask-specific workspace and/or working on the given task, and/or otherinformation. The one or more documents, updates, and/or otherinformation may be determined based on other generated work, documents,applications, and/or other information from one or more dependent tasks,similar tasks, associated tasks, and/or tasks that are otherwise linked.In some implementations, user task component 112 may be configured todetermine and/or effectuate presentation of one or more recommendedapplications, documents, updates, and/or other information based on oneor more updates, interactions, and/or events within a given task,project, and/or task-specific workspace that occurred while the givenuser was not in the task-specific workspace and/or working on the giventask. As such, the state of a given task-specific workspace may bemaintained while a user is not working on the given task and/or withinthe given task-specific workspace.

User task component 112 may be configured to effectuate presentation ofthe first task for the first user based on the environment stateinformation. Responsive to the first user selecting the first task, usertask component 112 may be configured to request information associatedwith the first task from environment state component 108. Informationassociated with the first task may include user state informationassociated with the first user (e.g., the first user record), projectstate information associated with a first project (e.g., the firstproject record) under which the first task may be assigned to the firstuser, task state information associated with the first task (e.g., thefirst task record), and/or other information. User task component 112may be configured to receive the environment state informationassociated with the first task such that the first task may be presentedto the first user.

In some implementations, desktop component 114 may be configured toclear the current desktop of a given client computing platform 124.Desktop component 114 may be configured to clear the current desktop toinitiate the first task-specific workspace for the first task. Thecurrent desktop may be cleared by minimizing and/or closing one or moreopen applications and/or windows displayed on the current desktop.Desktop component 114 may be configured to clear the current desktopresponsive to the current desktop including one or more openapplications or windows, and/or responsive to user task component 112receiving user input receiving user input indicating selection of afirst task.

Workspace component 116 may be configured to effectuate presentation ofthe first task-specific workspace for the first task. In someimplementations, the first task specific workspace may include a taskheader bar including one or more of a task name and/or an indication ofthe first task that the user is working on within the firsttask-specific workspace, a project the task is associated with, a duedate, a timer button (e.g., for timing how long a user works on a giventask), a status button (e.g., for indicating when a task is complete), achat and/or message button (e.g., for initiating a comment and/or chatsession re the first task, and/or other information.

One or more applications may be available via the task-specificworkspace. The user may use the one or more applications while workingon the given task associated with the task-specific workspace. By way ofnon-limiting example, the applications may include: one or more internetapplications (e.g., Internet Explorer, Chrome, etc.), one or moredocument applications (e.g., Microsoft Word, Pages, Adobe Acrobat,Writer, etc.), one or more presentation applications (e.g., PowerPoint,Keynote, etc.), one or more email applications (e.g., Outlook, Gmail,Yahoo mail, etc.), one or more messaging applications (e.g., Slack,Skype, etc.), one or more spreadsheet applications (e.g., Excel,Numbers, etc.), one or more photo/video applications (e.g., photoshop,iPhoto, iMovie, Adobe, Vegas Pro, etc.), and/or other applications(e.g., Genome browser, etc.). In some implementations, a first set ofapplications may be accessible via the first task-specific workspace.The first set of applications may have one or more corresponding windowsthrough which the first user interacts with the first set ofapplications.

The first set of applications may comprise the available applicationswithin the first task-specific workspace. In some implementations, thefirst set of applications may not include all of the applicationsaccessible via the first-task specific workspace. As such, one or moreapplications in addition to those from the first set of applications mayand/or may not be accessible within the first task-specific workspace.In some implementations, the first set of applications may include oneor more applications the first user interacts with while working on thefirst task within the first task specific workspace.

In some implementations, one or more other applications generallyavailable via the first client computing platform outside of thetask-specific workspace may not be accessible within the firsttask-specific workspace. Workspace component 116 may be configured toblock and/or restrict one or more applications. In some implementations,workspace component 116 may be configured to determine one or more otherapplications that are not accessible within the first task-specificworkspace. Workspace component 116 may be configured to determine whichapplications are not accessible based on one or more values for one ormore of the user parameters, the project parameters, the taskparameters, and/or other parameters indicating the one or more otherapplications are restricted while the first user is working on the firsttask via the first task specific workspace. In some implementations, theuser parameters, project parameters, task parameters, and/or otherparameters indicating the one or more other restricted applications mayinclude task settings and/or user settings indicating which applicationsto restrict and/or make available for the first task-specific workspace.In some implementations, a user (e.g., the first user, a project and/ortask owner, etc.) may determine the user settings.

Workspace component 116 may be configured to receive user inputindicating a pause and/or completion of the first task at a first time.The user input may be received via a pause button within thetask-specific workspace. In some implementations, wherein thetask-specific workspace has an integrated timer, pausing a task maycause the timer to pause. User input indicating a pause and/orcompletion of the first task may include switching from one task toanother (e.g., via selecting another task). In some implementations, theuser input indicating a pause of the first task at the first time mayinclude a selection of a second task.

Application component 118 may be configured to obtain informationcharacterizing interactions of the users with the applications withinthe task-specific workspaces at or near the time the task is paused. Insome implementations, application component 118 may be configured toobtain information characterizing interactions of the first user withthe first set of applications within the first task-specific workspaceat or near the first time. Interactions of the first user with the firstset of applications within the first task-specific workspace mayinclude, for example, one or more of information indicating whichapplications the user had open; which webpages, documents, and/or filesthe user had open; the application and/or document titles the user wasworking on and/or had open; progress information characterizing progressof the first user within the first set of applications (e.g., where theuser left off in one or more webpages and/or files) and/or on the firsttask (e.g., the user paused the task when 60% completed), an amount oftime spent on active applications, documents, and/or webpages; and/orother interactions. In some implementations, application component 118may be configured to monitor interactions of the first user with thefirst set of applications within the first task-specific workspace. Theinteractions may be monitored until the first time such that the stateof the first set of applications at the first time may be obtained.

Application component 118 may be configured to store the informationcharacterizing the interactions of the first user with the first set ofapplications at or near the first time as part of a first user recordand/or a first task record. In some implementations, applicationcomponent 118 may be configured to effectuate transmission of the firstuser record and/or the first task record over network 132 to environmentstate component 108 to store as part of one or more user records 128and/or task records 132 in electronic storage 126.

Returning to workspace component 116, workspace component 116 may beconfigured to minimize and/or close the one or more windowscorresponding to the first set of applications for the first task. Insome implementations, responsive to receiving the user input indicatingthe pause and/or the completion of the first task, workspace component116 may be configured to effectuate presentation of an option to saveand/or store the first task-specific workspace and/or the interactionsof the first user with the first set of applications within the firsttask-specific workspace. In some implementations, the first-taskspecific workspace and/or the interactions of the first user with thefirst set of applications within the first task-specific workspace maybe automatically stored responsive to the user pausing the first task,switching tasks, completing the first task and/or otherwise indicating apause of the first task. In some implementations, workspace component116 may effectuate presentation of an option to save the task-specificworkspace responsive to the user indication the status of thetask-specific workspace is complete (e.g., the user changing the statusfrom incomplete to complete).

In some implementations, responsive to receiving the user inputindicating the pause and/or the completion of the first task, workspacecomponent 116 may be configured to effectuate presentation of an optionto send a notification based on progress of the first user in the firsttask to one or more interested parties. The one or more interestedparties may be defined by the environment state information. By way ofnon-limiting example, when the user input indicates the first task ispaused (e.g., the user pauses the task and/or switches tasks) and/orcompleted, workspace component 116 may be configured to effectuatepresentation of an option to send a notification indicating the statusand/or progress of the task to one or more followers, team-members,dependent task assignees, project owners, dependent task followersand/or team members, and/or other interested parties.

Workspace component 116 may be configured to restore one of moreapplications based on the state information responsive to a userre-opining and/or re-starting a task and/or a task-specific workspace.In some implementations, workspace component may be configured torestore the first set of applications based on the environment stateinformation. The first set of applications may be restored by workspacecomponent 116 responsive to receiving information indicatingre-selection of the first task and/or a re-start of the first task. Thefirst set of applications and/or the one or more windows correspondingto the first set of applications may be restored based on the first userrecord and/or the first task record. As such, for example, the firstuser may be able to pick up working on the first task where he or sheleft off (e.g., with the correct applications open, on the right page,etc.).

Re-selecting and/or re-starting a given task may include initiatingstart of a given task after a user has previously worked on the giventask within the given task-specific workspace. In some implementations,the same user and/or a different user may re-start and/or re-select thegiven task. A different user may re-select and/or re-start the giventask and/or the given task-specific workspace even if the user has notpreviously worked on the given task within the given workspace. In someimplementations, if a first user selects and/or initiates the giventask-specific workspace, a second user may re-select and/or re-start thegiven task and/or the given task-specific workspace (e.g., even thoughthe second user may and/or may not have previously worked on the giventask and/or within the given task-specific workspace).

In some implementations, the task-specific workspace may be associatedwith and/or assigned to a given task (instead of an/or in addition to agiven user). As such, the task-specific workspace may be transferablesuch that another user may be able to pick up working on the task wherethe first user left off. As such, tasks may be re-assigned and/ortransferred to other users without losing progress on the task.

Restoring the first set of applications may include un-minimizing and/oropening the one or more windows corresponding to individual ones of thefirst set of applications the first user was working on at and/or nearthe first time. In some implementations, restoring the first set ofapplications may include un-minimizing, re-opening, arranging, closing,minimizing but opening to the correct page, and/or otherwise restoringthe first set of applications and/or corresponding windows to the statethey were in at or near the first time. Such that, by way ofnon-limiting example, responsive to the first user only interacting withone application within the first set of applications at the first time,the one application and/or corresponding window may be restored (e.g.,un-minimized, re-opened, closed, minimized but open to the correct page,and/or otherwise restored to the state it was in at or near the firsttime) when the first user returns to the first task-specific workspace.

By way of non-limiting example, responsive to the first user interactingwith six different applications (four active and two minimized) withinthe first set of applications at the first time, the four activeapplications and/or corresponding window may be restored (e.g.,un-minimized, re-opened, open to the correct page, and/or otherwiserestored to the state they were in at or near the first time) and thetwo minimized applications and/or corresponding window may be restored(e.g., minimized but loaded to the correct page/location, and/orotherwise restored to the state they were in at or near the first time)when the first user returns to the first task-specific workspace.

In some implementations, responsive to a user re-starting and/orre-initiating a given task from a different computer than used topreviously interact with the task-specific workspace for the given task,restoring one or more of the applications in a given set of applicationsmay include identifying one or more corresponding applications that aresimilar to the applications previously used within the task specificworkspace and/or restoring the one or more corresponding applications.By way of non-limiting example, if the first task-specific workspace isfirst presented on a first computer and all of the applications withinfirst set of applications are not available on a second computer used tore-start and/or re-initiate the first task, one or more correspondingapplications may be restored based on the first environment stateinformation responsive to a given user re-selecting and/or re-startingthe first task via the second computer. The one or more correspondingapplications may perform the same and/or similar functions as the one ormore applications to which they correspond.

By way of non-limiting example, if the first computer is an Applecomputer, the second computer is a PC, and/or one of the applications inthe first set of applications is Safari, the corresponding applicationmay include google Chrome on the second computer. In someimplementations, user preferences may be taken into account to determineone or more corresponding applications to recommend to a given user. Byway of non-limiting example, responsive to internet explorer beingpresent on the first computer and/or both internet explorer and Chromebeing present on the second computer, workspace component 116 maydetermine Chrome should be recommended (e.g., based on the user records,user preferences, etc.) responsive to a given user re-selecting and/orre-starting the first task via the second computer.

In some implementations, workspace component 116 may be configured torestore one of more applications based on the state informationincluding one or more interactions and/or updates that occurred whilethat first user was not working on the first task and/or within thefirst task-specific workspace. Other users may interact with the firsttask and/or the first task specific workspace while the first user isnot. As such, by way of non-limiting example, if a second user worked onthe first task after the first user paused the first task, theinteractions and/or progress of the second user on the first task and/orwithin the first task-specific workspace may be captured within thestate information such that when restored by the first user, theinteractions and/or progress of the second user may be reflected. Insome implementations, the state of the first task and/or the firsttask-specific workspace may be updated based on user interactions,updates and/or work product by one or more other users and/orinteractions, updates, and/or work product from one or more relatedtasks (e.g., dependent tasks, etc.), projects, and/or other information.

In some implementations, task-specific workspace may include a groupworkspace that is updated and/or restored according to the stateinformation reflecting interactions and/or progress of one or more usersin the group. By way of non-limiting example, some interactions,applications, and/or progress may be user-specific such that thetask-specific workspace tracks the state of the task-specific workspaceas a whole and/or for individual users within the group of users.

In some implementations, responsive to a user switching from a firsttask to a second task, workspace component 116 may be configured toeffectuate presentation of a second task-specific workspace. User taskcomponent 112 may be configured to receive user input indicatingselection of the second task. The second task may be another taskassigned to the first user and/or presented to the first user via thecollaboration environment. User task component 112 may effectuatepresentation of the second task for the first user based on theenvironment state information.

Workspace component 116 may be configured to effectuate presentation ofa second task-specific workspace for the second task. A second set ofapplications may be accessible via the second task-specific workspace.The second set of applications may have one or more correspondingwindows through which the first user interacts with the second set ofapplications. One or more applications in the second set of applicationsmay be different than the applications in the first set of applications.

Workspace component 116 may be configured to receive user inputindicating a pause and/or completion of the second task, and/or are-selection of the first task and/or another task at a second time.Application component 118 may be configured to obtain informationcharacterizing interactions of the first user with the second set ofapplications within the second task-specific workspace at or near thesecond time.

Application component 118 may be configured to store the informationcharacterizing the interactions of the first user with the second set ofapplications at or near the second time as a second user record and/or asecond task record, Workspace component 116 may be configured tominimize and/or close the one or more windows corresponding to thesecond set of applications for the second task.

Workspace component 116 may be configured to restore the second set ofapplications based on the environment state information. The second setof applications may be restored responsive to responsive to receivinginformation indicating re-selection of the first task and/or anothertask, and/or pausing of the second task. The one or more windowscorresponding to the second set of applications may be restored based onthe second user record and/or the second task record.

By way of non-limiting illustration, FIG. 2A illustrates an exemplarygraphical user interface for initiating a task-specific workspace, inaccordance with one or more implementations. Desktop 200 may bepresented via a client computing platform the same as or similar to oneof client computing platform(s) 124. Desktop 200 may include graphicaluser interface (GUI) 202. GUI 202 may be configured to effectuatepresentation of task 210 to which the user is assigned. GUI 202 maypresent a greeting 201, description of task 210, due date 212, assignee214, and/or other information associated with task 210. Greeting 210 maywelcome the user and/or indicate how much time the user has to work ontask 210. In some implementations, one or more other tasks may bepresented in addition to task 210. By way of non-limiting example, task210 may be a highest priority task indicated by a high priority field204 based on it having a higher priority than the three other tasksassigned to the user, an earlier due date, one or more dependent tasks,and/or other information. GUI 202 may be presented to the user in orderto initiate a task-specific workspace. Responsive to the user clickingon button 206 to begin task 210, a task-specific workspace for task 210may be initiated.

By way of non-limiting illustration, FIG. 2B illustrates an exemplaryapplication recommendation interface for a task-specific workspace, inaccordance with one or more implementations. In some implementations,application recommendation interface 250 may present one or morerecommended applications 252 for task 210 responsive to the userselecting and/or initiating work on task 210. Application recommendationinterface 250 may include a “launch all” button 254 that enables theuser to launch all of recommended applications 252. By way ofnon-limiting example, one or more of recommended applications 252 may bedetermined based on user information (e.g., historical user information,user preferences, etc.); task information (e.g., a type of task, thetask title, the task due date, etc.); generated work, documents,applications used, and/or other information from one or more dependenttasks, similar tasks, associated tasks, and/or tasks that are otherwiselinked to task 210; one or more updates, interactions, and/or eventswithin a given task, project, and/or task-specific workspace; and/or oneor more updates, interactions, and/or events within a given task,project, task-specific workspace that occurred while the given user wasnot in the task-specific workspace and/or working on the given task,and/or other information.

By way of non-limiting illustration, FIG. 2C illustrates an exemplarytask-specific workspace, in accordance with one or more implementations.Task-specific workspace 216 may include a first set of applications 218that are accessible via task-specific workspace 216. Window 220 maycorrespond with one of the applications in the first set of applications218. Task-specific workspace 216 may include a header 217. Header 217may include task information describing task 210. Header 217 may includeone or more buttons. Status button 222 may be used by the user toindicate task 210 is complete and/or incomplete, and/or triggercompletion of task 210. Pause button 224 may be used to pause task 210and/or a timer associated with task 210. Chat button 226 may be used toinitiate a chat session related to task 210 and/or make a comment ontask 210. Header 217 may display the due date 212 of task 210. In someimplementations, header 217 may display a quantity of tasks waiting 216(e.g., lower priority tasks and/or tasks not presently selected by theuser). Header 217 may indicate what a user should be working on suchthat the user remains focused on task 210.

By way of non-limiting illustration, FIG. 2D illustrates an exemplarygraphical user interface for pausing a task-specific workspace, inaccordance with one or more implementations. Graphical user interface(GUI) 228 may be presented to the user responsive to the user selectingthe pause button 224 (see e.g., FIG. 2C). In some implementations, (notpictured) GUI 228 may present an option to save and/or store the firsttask-specific workspace and/or the interactions of the first user withfirst set of applications 218 within the first task-specific workspace216. In some implementations, GUI 228 may present a notification 230 ofthe interactions in the task-specific workspace it is saving. GUI 228may include options 232 to send one or more notifications based onprogress of the user in the task to one or more interested parties(e.g., followers, team members, dependent task assignees, and/or otherinterested parties. In some implementations, the one or more interestedparties may be defined by the environment state information.

Responsive to the first user re-starting and/or re-selecting the firsttask, first set of applications 218 may be restored based on theenvironment state information. In some implementations, responsive tothe first user re-starting and/or re-selecting the first task, theexemplary task-specific workspace as illustrated in FIG. 2C may bepresented to the first user. As such, the individual application offirst set of applications 218 and its corresponding window 220 may berestored based on the environment state information. One or more otherapplications in first set of applications 218 may also be restored asopen, but the windows may be minimized and/or behind window 220 becausethe interactions of the user when the user paused the task 210 indicatedthe workspace state (e.g., including the application state and/or windowstate) illustrated in FIG. 2C.

Returning to FIG. 1, in some implementations, one or more servers 102,one or more client computing platforms 124, and/or external resource(s)122, may be operatively linked via one or more electronic communicationlinks. For example, such electronic communication links may beestablished, at least in part, via a network 132 such as the Internetand/or other networks. It will be appreciated that this is not intendedto be limiting, and that the scope of this disclosure includesimplementations in which one or more servers 102, one or more clientcomputing platforms 124, and/or external resource(s) 122, may beoperatively linked via some other communication media.

The external resource(s) 122 may include sources of information,external entities participating with system 100, and/or other resources.In some implementations, some or all of the functionality attributedherein to external resource(s) 122 may be provided by resources includedin system 100.

The one or more servers 102 may include communication lines, or ports toenable the exchange of information with a network and/or other computingplatforms. Illustration of one or more servers 102 in FIG. 1 is notintended to be limiting. One or more servers 102 may include a pluralityof hardware, software, and/or firmware components operating together toprovide the functionality attributed herein to one or more servers 102.For example, one or more servers 102 may be implemented by a cloud ofcomputing platforms operating together as one or more servers 102.

Processor(s) 104 and/or processor(s) 105 may be configured to provideinformation processing capabilities in one or more servers 102. As such,processor(s) 104 and/or processor(s) 105 may include one or more of adigital processor, an analog processor, a digital circuit designed toprocess information, an analog circuit designed to process information,a state machine, and/or other mechanisms for electronically processinginformation. Although processor(s) 104 and/or processor(s) 105 are shownin FIG. 1 as a single entity, this is for illustrative purposes only. Insome implementations, processor(s) 104 and/or processor(s) 105 mayinclude a plurality of processing units. These processing units may bephysically located within the same device, or processor(s) 104 and/orprocessor(s) 105 may represent processing functionality of a pluralityof devices operating in coordination. The processor(s) 104 and/orprocessor(s) 105 may be configured to execute computer readableinstruction components 108, 110, 112, 114, 116, 118, and/or othercomponents. The processor(s) 104 and/or processor(s) 105 may beconfigured to execute components 108, 110, 112, 114, 116, 118, and/orother components by software; hardware; firmware; some combination ofsoftware, hardware, and/or firmware; and/or other mechanisms forconfiguring processing capabilities on processor(s) 104 and/orprocessor(s) 105.

It should be appreciated that although components 108 and/or components110, 112, 114, 116, and/or 118 are illustrated in FIG. 1 as beingco-located within a single processing unit, in implementations in whichprocessor(s) 104 and/or processor(s) 105 include multiple processingunits, one or more of components 108, 110, 112, 114, 116, and/or 118 maybe located remotely from the other components. The description of thefunctionality provided by the different components 108, 110, 112, 114,116, and/or 118 described herein is for illustrative purposes, and isnot intended to be limiting, as any of components 108, 110, 112, 114,116, and/or 118 may provide more or less functionality than isdescribed. For example, one or more of components 108, 110, 112, 114,116, and/or 118 may be eliminated, and some or all of its functionalitymay be provided by other ones of components 108, 110, 112, 114, 116,and/or 118. As another example, processor(s) 104 and/or processor(s) 105may be configured to execute one or more additional components that mayperform some or all of the functionality attributed herein to one ofcomponents 108, 110, 112, 114, 116, and/or 118.

FIG. 3 illustrates a method 300 for facilitating task-specificworkspaces for a collaboration work management platform, in accordancewith one or more implementations. The operations of method 300 presentedbelow are intended to be illustrative. In some implementations, method300 may be accomplished with one or more additional operations notdescribed, and/or without one or more of the operations discussed.Additionally, the order in which the operations of method 300 areillustrated in FIG. 3 and described below is not intended to belimiting.

In some implementations, method 300 may be implemented in one or moreprocessing devices (e.g., a digital processor, an analog processor, adigital circuit designed to process information, an analog circuitdesigned to process information, a state machine, and/or othermechanisms for electronically processing information). The one or moreprocessing devices may include one or more devices executing some or allof the operations of method 300 in response to instructions storedelectronically on an electronic storage medium. The one or moreprocessing devices may include one or more devices configured throughhardware, firmware, and/or software to be specifically designed forexecution of one or more of the operations of method 300.

At an operation 302, presentation of a collaboration environment may beeffectuated based on environment state information. The environmentstate information may include user records, project records, taskrecords, and/or other records. The environment state information maydefine a state of the collaboration environment. The state of thecollaboration environment may include a user state, a project state, atask state, and/or other states. The user state may be defined by theuser records. The user records may define values of user parametersassociated with users interacting with and/or viewing the collaborationenvironment. The project state may be defined by the project records.The project records may define values of project parameters for projectsmanaged within the collaboration environment. The task state may bedefined by the task records. The task records may define values of taskparameters for tasks created and/or assigned within the collaborationenvironment. In some embodiments, operation 302 is performed by acollaboration environment component the same as or similar tocollaboration environment component 110 (shown in FIG. 1 and describedherein).

At an operation 304, task-specific workspaces for individual ones of theusers for individual ones of the tasks may be facilitated. A firsttask-specific workspace for a first user may be facilitated on a firstclient computing platform. In some embodiments, operation 304 isperformed by a collaboration environment component the same as orsimilar to collaboration environment component 110 (shown in FIG. 1 anddescribed herein).

At an operation 306, user input indicating selection of a first task maybe received. In some embodiments, operation 306 is performed by a usertask component the same as or similar to user task component 112 (shownin FIG. 1 and described herein).

At an operation 308, presentation of the first task may be effectuatedfor the first user based on the environment state information. In someembodiments, operation 308 is performed by a user task component thesame as or similar to user task component 112 (shown in FIG. 1 anddescribed herein).

At an operation 310, presentation of the first task-specific workspacemay be effectuated for the first task. A first set of applications maybe accessible via the task-specific workspace. The first set ofapplications may have one or more corresponding windows through whichthe first user interacts with the first set of applications. In someembodiments, operation 310 is performed by a workspace component thesame as or similar to workspace component 116 (shown in FIG. 1 anddescribed herein).

At an operation 312, user input indicating a pause and/or completion ofthe first task may be received. The pause and/or completion of the firsttask may be at a first time. In some embodiments, operation 312 isperformed by a workspace component the same as or similar to workspacecomponent 116 (shown in FIG. 1 and described herein).

At an operation 314, information characterizing interactions of thefirst user with the first set of applications within the firsttask-specific workspace at or near the first time may be obtained. Insome embodiments, operation 314 is performed by an application componentthe same as or similar to application component 118 (shown in FIG. 1 anddescribed herein).

At an operation 316, the information characterizing the interactions ofthe first user with the first set of applications at or near the firsttime may be stored. The information may be stored as part of a firstuser record and/or a first task record. In some embodiments, operation316 is performed by an application component the same as or similar toapplication component 118 (shown in FIG. 1 and described herein).

At an operation 318, the one or more windows corresponding to the firstset of applications for the first task may be minimized and/or closed.In some embodiments, operation 318 is performed by a workspace componentthe same as or similar to workspace component 116 (shown in FIG. 1 anddescribed herein).

At an operation 320, the first set of applications may be restored basedon the environment state information. The first set of applications maybe restored responsive to receiving information indicating re-selectionof the first task and/or a re-start of the first task. Such that he oneor more windows corresponding to the first set of applications may berestored based on the first user record and/or the first task record. Insome embodiments, operation 320 is performed by a workspace componentthe same as or similar to workspace component 116 (shown in FIG. 1 anddescribed herein).

Although the system(s) and/or method(s) of this disclosure have beendescribed in detail for the purpose of illustration based on what iscurrently considered to be the most practical and preferredimplementations, it is to be understood that such detail is solely forthat purpose and that the disclosure is not limited to the disclosedimplementations, but, on the contrary, is intended to covermodifications and equivalent arrangements that are within the spirit andscope of the appended claims. For example, it is to be understood thatthe present disclosure contemplates that, to the extent possible, one ormore features of any implementation can be combined with one or morefeatures of any other implementation.

What is claimed is:
 1. A system configured to facilitate task-specificworkspaces within a collaboration environment, the system comprising:one or more physical processors configured by machine-readableinstructions to: manage environment state information maintaining acollaboration environment, the environment state information includinguser records and task records, the user records including userinformation describing users interacting with and/or viewing thecollaboration environment, the task records task information describingtasks created within the collaboration environment and assigned withinthe collaboration environment to the users who are expected toaccomplish one or more actions to complete the tasks; effectuatepresentation of a first task-specific workspace for a first task on afirst computing platform associated with a first user, wherein thetask-specific workspace presents a first set of applications via one ormore windows through which the first user interacts with the first setapplications; receive user input including a selection of a second taskpreviously assigned to the first user from a list of multiple taskspreviously assigned to the first user, the user input indicating a pauseof the first task; responsive to receiving the user input: storeinteraction information characterizing interactions of the first userwith the first set of applications in a first task record of the firsttask; and close the one or more windows corresponding to the first setof applications; and responsive to receiving restart informationindicating a re-start of the first task, restore the first set ofapplications within the first task-specific workspace such that the oneor more windows corresponding to the first set of applications arerestored based on the first task record.
 2. The system of claim 1,wherein the one or more physical processors are further configured bythe machine-readable instructions to: clear a current desktop toinitiate the first task-specific workspace for the first task byminimizing and/or closing one or more other windows displayed on thecurrent desktop.
 3. The system of claim 1, wherein one or more otherapplications available via the first computing platform outside of thefirst task-specific workspace are made inaccessible within the firsttask-specific workspace.
 4. The system of claim 3, wherein the one ormore physical processors are further configured by the machine-readableinstructions to: identify the one or more other applications as beinginaccessible within the first task-specific workspace based on the userrecords and/or the task records.
 5. The system of claim 1, wherein theinteraction information characterizing the interactions of the firstuser with the first set of applications includes progress informationcharacterizing progress of the first user within the first set ofapplications and/or on the first task.
 6. The system of claim 1, whereinthe one or more physical processors are further configured by themachine-readable instructions to close, responsive to receiving the userinput, the first task-specific workspace.
 7. The system of claim 1,wherein the one or more physical processors are further configured bythe machine-readable instructions to effectuate presentation of anoption to save and/or store the first task-specific workspace and/or theinteractions of the first user with the first set of applications withinthe first task-specific workspace.
 8. The system of claim 1, wherein theone or more physical processors are further configured by themachine-readable instructions to effectuate presentation of an option tosend a notification based on progress of the first user on the firsttask to one or more other ones of the users.
 9. The system of claim 1,wherein the one or more physical processors are further configured bythe machine-readable instructions to: responsive to receiving the userinput including the selection of the second task, effectuatepresentation of a second task-specific workspace for the second task.10. The system of claim 1, wherein the presentation of the firsttask-specific workspace for the first task is responsive to a selectionof the first task from the list of multiple tasks previously assigned tothe first user.
 11. A method to facilitate task-specific workspaceswithin a collaboration environment, the method comprising: managingenvironment state information maintaining a collaboration environment,the environment state information including user records and taskrecords, the user records including user information describing usersinteracting with and/or viewing the collaboration environment, the taskrecords task information describing tasks created within thecollaboration environment and assigned within the collaborationenvironment to the users who are expected to accomplish one or moreactions to complete the tasks; effectuating presentation of a firsttask-specific workspace for a first task on a first computing platformassociated with a first user, wherein the task-specific workspacepresents a first set of applications via one or more windows throughwhich the first user interacts with the first set applications;receiving user input including a selection of a second task previouslyassigned to the first user from a list of multiple tasks previouslyassigned to the first user, the user input indicating a pause of thefirst task; responsive to receiving the user input: storing interactioninformation characterizing interactions of the first user with the firstset of applications in a first task record of the first task; andclosing the one or more windows corresponding to the first set ofapplications; and responsive to receiving restart information indicatinga re-start of the first task, restoring the first set of applicationswithin the first task-specific workspace such that the one or morewindows corresponding to the first set of applications are restoredbased on the first task record.
 12. The method of claim 11, furthercomprising: clearing a current desktop to initiate the firsttask-specific workspace for the first task by minimizing and/or closingone or more other windows displayed on the current desktop.
 13. Themethod of claim 11, wherein one or more other applications available viathe first computing platform outside of the first task-specificworkspace are made inaccessible within the first task-specificworkspace.
 14. The method of claim 13, further comprising: identifyingthe one or more other applications as being inaccessible within thefirst task-specific workspace based on the user records and/or the taskrecords.
 15. The method of claim 11, wherein the interaction informationcharacterizing the interactions of the first user with the first set ofapplications includes progress information characterizing progress ofthe first user within the first set of applications and/or on the firsttask.
 16. The method of claim 11, further comprising closing, responsiveto receiving the user input, the first task-specific workspace.
 17. Themethod of claim 11, further comprising effectuating presentation of anoption to save and/or store the first task-specific workspace and/or theinteractions of the first user with the first set of applications withinthe first task-specific workspace.
 18. The method of claim 11, furthercomprising effectuating presentation of an option to send a notificationbased on progress of the first user on the first task to one or moreother ones of the users.
 19. The method of claim 11, further comprising:responsive to receiving the user input including the selection of thesecond task, effectuating presentation of a second task-specificworkspace for the second task.
 20. The method of claim 11, wherein thepresentation of the first task-specific workspace for the first task isresponsive to a selection of the first task from the list of multipletasks previously assigned to the first user.